Hi All,
This is possibly a trivial mistake ... but I never came across it
before.
I have a search form for searching Lucene. Mozilla confirms the page is
in UTF-8 encoding.
I enter a string with accented characters into the query field. eg
'éclair' (e-acute).
The form comes back
UTF-8. (The value
has been picked up by an InputModule and fed via the SiteMap to XSLT).
The query string in the URL reads 'query=%C3%A9clair', which are the
unicodes for 'A-tilde' and 'Copyright' characters. (Which would imply to
me that the Browser incorrectly encoded the query.)
How do other
encoding problems
Hi All,
This is possibly a trivial mistake ... but I never came across it
before.
I have a search form for searching Lucene. Mozilla confirms
the page is
in UTF-8 encoding.
I enter a string with accented characters into the query field. eg
'éclair' (e-acute
characters into the query field. eg
'éclair' (e-acute).
The form comes back with the string now reading 'éclair'. (A-tilde,
Copyright sign). Mozilla says the encoding is still UTF-8. (The value
has been picked up by an InputModule and fed via the SiteMap to XSLT).
The query string in the URL reads
in NS/Mozilla. Sorry, cannot really remember what is was :-/
Have a beer, maybe you will remember ;)
I have a search form for searching Lucene. Mozilla confirms the page
is in UTF-8 encoding.
I enter a string with accented characters into the query field. eg
'clair' (e-acute).
The form comes back
+xsl:template match="esql:row-results//esql:get-string-by-variable"
name="get-string-by-variable"
+ xsp:expr
+ xsl:call-template name="get-string-encoded"
+ xsl:with-param name="column-spec"xsl:value-of
select="@column"//xsl:with-param
+ xsl:with-
it not make more sense to put this functionality into a specialised
utility class for manipulating a request query string - SOC and all that...
BTW, what is a MultiPartRequest?
A special implementation of Request to decode and provide access to
MIME-multipart encoded submissions (required for posting
have such functionallity somewhere?
Does it not make more sense to put this functionality into a specialised
utility class for manipulating a request query string - SOC and all that...
But the Request object is used nearly everywhere in cocoon.
And with the extended Request we have nothing
;
-byte[] buffer = null;
+/** returns Unicode encoded string from CLOB or String column
+ */
+public final static String getStringOrClob(ResultSet set, String column) throws
RuntimeException {
+
+String result = null;
try {
-Clob
(Error getting clob data: +
e.getMessage());
}
@@ -153,10 +156,11 @@
/** returns Unicode encoded string from CLOB or String column
*/
-public final static String getStringOrClob(ResultSet set, int column) throws
java.lang.Exception {
+public final static
-xsp:expr
- xsl:call-template name=get-string-encoded
-xsl:with-param name=column-spec_esql_i/xsl:with-param
-xsl:with-param
name=resultset_esql_query.resultset/xsl:with-param
- /xsl:call-template
-/xsp:expr
/
+ /xsp:content
+/xsl:template
+
xsl:template match=esql:execute-query//esql:error-results
xsp:content
xsl:apply-templates/
@@ -781,7 +840,7 @@
/xsl:template
xspdoc:descreturns the value of the given column as a string/xspdoc:desc
-xsl:template match=esql:row-results//esql:get
-xsp:expr
- xsl:call-template name=get-string-encoded
-xsl:with-param name=column-spec_esql_i/xsl:with-param
-xsl:with-param
name=resultset_esql_query.resultset/xsl:with-param
- /xsl:call-template
-/xsp:expr
the
type-specific get methods and write out the result fragment yourself./xspdoc:desc
@@ -644,12 +738,35 @@
/xsl:otherwise
/xsl:choose
/xsp:param
-xsp:expr
- xsl:call-template name=get-string-encoded
-xsl:with-param
)
- /xsl:otherwise
-/xsl:choose
- );
- _esql_node.appendChild(document.createTextNode(
-xsl:call-template name=get-string-encoded
- xsl:with-param name=column-spec_esql_i/xsl:with-param
- xsl:with-param
name
- );
- _esql_node.appendChild(document.createTextNode(
-xsl:call-template name=get-string-encoded
- xsl:with-param name=column-spec_esql_i/xsl:with-param
- xsl:with-param
name=resultset_esql_query.getResultSet()/xsl:with-param
-/xsl:call-template
be
+unique within the form, but it is most convenient to name the view after
+the base of the filename. So in this case, we will name our view
+#34;registration#34;. In step 4 static string constants are used to unify
+the naming and allow for easier maintenance /p
logic in the action. The name of the view should simply be
+unique within the form, but it is most convenient to name the view after
+the base of the filename. So in this case, we will name our view
+#34;registration#34;. In step 4 static string constants are used
18 matches
Mail list logo
